Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency node-fetch to v2.6.7 [security] - autoclosed #209

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 11, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
node-fetch 2.6.1 -> 2.6.7 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2022-0235

node-fetch forwards secure headers such as authorization, www-authenticate, cookie, & cookie2 when redirecting to a untrusted site.


node-fetch forwards secure headers to untrusted sites

CVE-2022-0235 / GHSA-r683-j2x4-v87g

More information

Details

node-fetch forwards secure headers such as authorization, www-authenticate, cookie, & cookie2 when redirecting to a untrusted site.

Severity

  • CVSS Score: 8.8 / 10 (High)
  • Vector String: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Release Notes

node-fetch/node-fetch (node-fetch)

v2.6.7

Compare Source

Security patch release

Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred

What's Changed

Full Changelog: node-fetch/node-fetch@v2.6.6...v2.6.7

v2.6.6

Compare Source

What's Changed

Full Changelog: node-fetch/node-fetch@v2.6.5...v2.6.6

v2.6.5

Compare Source

v2.6.4

Compare Source

v2.6.3

Compare Source

v2.6.2

Compare Source

fixed main path in package.json


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@lvpeschke lvpeschke requested a review from sissnad January 11, 2024 16:40
Copy link

socket-security bot commented Jan 11, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/[email protected] network +3 493 kB node-fetch-bot

🚮 Removed packages: npm/[email protected]

View full report↗︎

@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch 4 times, most recently from 587fb5c to c5ba3db Compare January 12, 2024 11:49
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from c5ba3db to 417b801 Compare February 15, 2024 15:40
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from 417b801 to cece77f Compare February 23, 2024 16:32
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch 3 times, most recently from 6dbb2c1 to a797f39 Compare March 18, 2024 15:16
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from a797f39 to efddb92 Compare March 22, 2024 16:40
@renovate renovate bot changed the title fix(deps): update dependency node-fetch to v2.6.7 [security] fix(deps): update dependency node-fetch to v2.6.7 [security] - autoclosed Apr 17, 2024
@renovate renovate bot closed this Apr 17, 2024
@renovate renovate bot deleted the renovate/npm-node-fetch-vulnerability branch April 17, 2024 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants